5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
- Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-7: Predefined Fields

Predefined Processes


APPX provides a number of standard processes in the runtime application that you can invoke, or are automatically invoked, at appropriate points in your applications.  For example, APPX contains a standard DISPOSITION input process that allows users to specify certain print-related information that controls how, when, and where a report is to print.To invoke this process as a child in an application, you identify the application ID as '---', the process type as INPUT, and the process name as DISPOSITION.

When you use a predefined process, you designate the application ID with three hyphens (---).  APPX interprets the three hyphens as the runtime application.  (The actual application ID is 0LA.)

You cannot modify any of the predefined processes, although you can, for example, develop your own version of a DISPOSITION process by defining an input process in your own application.  Then, instead of executing the runtime application's DISPOSITION process, you invoke the appropriate input process from your own application.

Some of the predefined processes are shown as Optional Child Processes on a menu below.

Some Predefined Processes Shown As Optional Child Processes

Application Design Manual                                         "Powered by Appx Software"

873

©2006 By APPX Software, Inc. All Rights Reserved